home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
1994.12.gz
/
1994.12
/
000073_gildea@x.org_Mon Dec 19 11:27:25 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-12-30
|
2KB
Received: from expo.x.org by cs.umb.edu with SMTP id AA19358
(5.65c/IDA-1.4.4 for <tex-k@cs.umb.edu>); Mon, 19 Dec 1994 16:27:29 -0500
Received: from alex.x.org by expo.x.org id AA26067; Mon, 19 Dec 94 16:27:27 -0500
Received: by alex.x.org id AA02855; Mon, 19 Dec 94 16:27:26 EST
Message-Id: <9412192127.AA02855@alex.x.org>
To: "K. Berry" <kb@cs.umb.edu>
Cc: tex-k@cs.umb.edu
Subject: Re: can't build TeX formats with TEXINPUTS set
In-Reply-To: Message from kb@cs.umb.edu of 18 Dec 94 6:47:28 EST
<199412181147.AA28623@terminus.cs.umb.edu>
Date: Mon, 19 Dec 1994 16:27:25 EST
From: Stephen Gildea <gildea@x.org>
So the feature of being able to insert the default path in my path has
been there all along. Well, I feel foolish, but I'm glad to see this.
I have now set my TEXINPUTS to a value that works with both my old TeX
setup and the newly built one. It seems I did know this once, because
I see my TEXFONTS setting uses it. So...a path element of "" means the
default path; I'm going to remember that this time.
> Oddly, setting TEXINPUTS to a null value seems to be the same as
> setting it to "." I consider this a bug. A null value should be the
> same as unsetting it,
>
> Yeah, maybe you're right, but it seems a painful thing to have to
> program around. I don't think it's odd ... But, you can
> work around this by setting the value to `:' -- see below.
Now that I understand what "" means, I'd like to argue for my
interpretation again, independent of the relative ease of setting to
null versus unsetting.
Start by noting the difference between these two two-element paths:
"foo:" != "foo:."
removing the common first element and the separating colon:
"" != "."
Q.E.D.
As another way of looking at it, a path of ":" contains two null path
elements. It should behave the same as "", which contains one null
path element, except it might take twice as long to complain about a
non-existent file.
< Stephen